System and method for generating a medical history

ABSTRACT

A system and method for generating a medical history that is determined based on the patient&#39;s medication list. Medications are taken for specific indications, i.e., disease and/or symptom, and the system includes a knowledge base of all known medications and associated indications. Preferably, an expert system allows the patient, nurse or other user, to enter all or part of the name of the patient&#39;s medications, and creates a list of probable medications by determining which of the known medications the patient most likely takes. Based on a user selected probable medication, the system creates a list of probable medical indications associated with the selected medication. Based on a user selected probable indication, the system generates a medical history for the patient. The probable medications and probable medical indications are determined preferably based on the patient&#39;s demographic data, historical data for other patients, and responses to follow-up questions generated by the system.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.12/259,273, filed Oct. 27, 2008, now U.S. Pat. No. 7,908,154.

FIELD

This invention relates to medical histories, and more specifically,relates to generating a medical history.

BACKGROUND

A detailed medical history is the cornerstone for accurate patientassessments and medical diagnosis. Traditional history taking byclinicians is often incomplete and time consuming because it requiresnot only collecting the information, but also accurately documenting it.Clinicians are typically highly paid medical professionals. A needexists, therefore, for a system that can take an accurate and completemedical history without the direct participation of costly medicalpersonnel.

Computerized systems are available for patients to enter medical datathemselves in response to queries. Typically, these systems use apredetermined set of questions for the patient, or another user onbehalf of the patient, to answer. These computerized systems areconsidered superior to traditional history taking techniques becausetypically such systems 1) are highly structured to include all pertinentquestions and never forget to ask a question; 2) can be done at thepatient's pace at a time and place that is convenient for the patient;3) elicit sensitive information that is often underreported in theface-to-face interview; 4) can be administered in different languages;5) prepare patients for the subsequent encounter with the clinician; 6)can calculate scores to clinical rating scales for easy interpretationby a physician; and 7) provide legible summaries that can be manipulatedby or directly entered into an electronic medical record.

A known automated computer-based medical history taking system isdescribed in U.S. Pat. No. 3,566,370 which provides for the developmentof and printout of a patient's medical history. The system includes adisplay for presenting questions with multiple choice answers to apatient. Subsequent questions are presented to the patient in accordancewith the answers to previous questions. Therefore, medically relatedquestions are automatically propounded according to U.S. Pat. No.3,566,370, even though not specifically selected for review by apatient.

Similarly, U.S. Pat. No. 7,290,016 describes a system and method forgenerating and storing a medical history that uses a questionnairedatabase in which answers to questions are correlated with subsequentquestions. The questionnaire database includes a plurality of questionsand corresponding multiple choice responses. The responses areassociated with additional questions in the questionnaire database.Therefore, the pattern through the questionnaire database is notpredetermined according to U.S. Pat. No. 7,290,016, but is dependentupon the pattern of answers.

While both of the above-mentioned systems and methods for eliciting amedical history are superior to traditional history taking techniques,i.e., by a clinician or paper questionnaire, these and other knownsystems and methods still have serious drawbacks that limit theireffectiveness and have hindered their widespread acceptance by bothpatients and the medical community at large.

First, these known computer based questionnaires contain too manyquestions, many of which are not relevant to the patient being asked thequestion, i.e., many questions are not patient specific. While knownsystems do employ branch-chain logic to hone in on specific patientcomplaints and clarify symptoms, these systems have no way ofidentifying which questions are the most important to ask the patientupfront. As such, these known systems require the patients to answer toomany irrelevant questions. Furthermore, patients make inadvertent errorsduring standard computer interviews of these known systems because thepatients misunderstand the questions, forget, and/or become tired andcareless. Studies such as noted by Carr have found that these drawbackslead to an error rate in patient directed computer interviews of 3%-7%.

There is a need, therefore, for a patient-driven computer based systemthat is not only highly patient specific, but also provides a “checksand balance” system for the patient to help eliminate some of the errorsthat occur from patients misunderstanding questions and/or forgetting orinadvertently misrepresenting certain components of their medicalhistory. There is also a need for the system to learn from both thepatient's particular situation and from the system's experience withprior users in order to provide more relevant questions to the patientin order to more readily obtain a more accurate medical history from thepatient.

SUMMARY

The system and method according to certain embodiments of the presentinvention substantially overcome the deficiencies of known systems andmethods by generating a medical history from the medications the patientis taking. A preferred embodiment comprises utilizing an expert systemand machine learning to deduce a patient's medical history from themedications the patient is taking.

Broadly stated, the present invention provides according to certainembodiments, a method for generating a medical history for a patient,comprising obtaining from a user an identification of each of themedications the patient is taking; for each one of the medications: (i)creating a list of probable medical indications associated with therespective medication, wherein the probable medical indications arediseases or symptoms; (ii) displaying the list to the user; and (iii)receiving selection from the user of one of the probable medicalindications from the list; and generating a medical history for thepatient based on the user selected probable medical indications andrespective medications.

Broadly stated, the present invention also provides according to certainembodiments, a system for generating a medical history for a patient,comprising: means for obtaining from a user an identification of each ofthe medications the patient is taking; for each one of the medications:(i) means for creating a list of probable medical indications associatedwith the respective medication, wherein the probable medical indicationsare diseases or symptoms; (ii) means for displaying the list to theuser; and (iii) means for receiving selection from the user of one ofthe probable medical indications from the list; and means for generatinga medical history for the patient based on the user selected probablemedical indications and respective medications.

These and other embodiments, features, aspects, and advantages of theinvention will become better understood with reference to the followingdescription, appended claims and accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an exemplary display regarding a survey questionregarding medications according to an embodiment of the presentinvention.

FIG. 2 illustrates a survey flowchart powered by the survey engineaccording to an exemplary embodiment of the present invention.

FIG. 3 illustrates a block diagram of a system according to certainembodiments of the present invention.

Reference symbols or names are used in the Figures to indicate certaincomponents, aspects or features shown therein, with reference symbolscommon to more than one Figure indicating like components, aspects orfeatures shown therein.

DETAILED DESCRIPTION

The system and method according to certain embodiments of the presentinvention is preferably implemented in a computer device. Any type ofgeneral purpose computer comprising one or more computers can be used.The computer may be a device, including but not limited to a personalcomputer, personal digital assistant (PDA), cellular phone, or the like.Alternatively, the system could be implemented on a special purposecomputer or a computer network specifically created to perform thefunctions of the present invention. Alternatively, the system could beimplemented on a server system connected to a wide area networkaccessible from any location connected to the network. According toanother alternative, certain embodiments of the invention may be used inconjunction with a call center, for example, wherein a person isprompted by their computer device to ask questions of the patient orother user, the computer device being operable to implement certainembodiments of the invention.

FIG. 3 is a block diagram of the System 100 implemented in accordancewith certain embodiments of the invention. System 100 includes UserInterface 200, Processing Subsystem 300, Expert System 400 and severaldatabases 500-900.

User Interface 200 is preferably a browser-based application that workswith Processing Subsystem 300 and Expert System 400 to perform thevarious functions of System 100 for creation and retrieval of medicalhistories. Preferably, the user (not shown) may use any suitable browser110 to access the User Interface 200 via the Internet 120 and a WebServer 130, as illustrated in FIG. 3.

Expert System 400 is at the core of System 100. An expert system,broadly defined, is a software system that attempts to reproduce theperformance of one or more human experts by analyzing information,usually supplied by the user of the system, and utilizing what appearsto be reasoning capabilities. Machine learning is concerned with thedesign and development of algorithms and techniques that allow computersto learn from either inductive or deductive reasoning. The Expert System400 in the exemplary System 100 according to the embodiment in FIG. 3generates successive survey questions whereby those questions areinformed via several inputs. Initially, those inputs are patientself-reported medications and, preferably, patient demographics. Basedon those initial inputs, Expert System 400 preferably draws upon severaldatabases in an iterative fashion: 1/Medication Database 600 that liststhe correct spelling of all known medications, both branded, generic,and homeopathic (e.g. herbal medications); 2/Medication associated withCondition Database 700, also referred to as “Medication/ConditionDatabase” 700, that links each of these medications to their indicateduses for all known relevant medical conditions and/or disease symptoms;both approved and not approved by the Federal Drug Administration (FDA)or similar global regulatory bodies; and 3/Data Warehouse Database 800which is populated with data from patients who have previously used thesystem.

The process of formulating a medical history using System 100 can beinitiated in one of several ways. According to one embodiment, acustomer-user, e.g., clinician or hospital administrator, accesses theSystem 100 via the User Interface 200 and enters a patient'sdemographics, e.g., age, gender, weight, vital signs, and assigns thepatient a password. This demographics and password data is used toinitiate the creation of a survey. Patient demographics are preferablystored in an anonymous fashion in the Survey Database 500;alternatively, demographics data including patient specific data isstored in the Survey Database 500.

FIG. 2 illustrates a survey flowchart 210 powered by the survey engineaccording to an exemplary embodiment of the present invention. Thepatient or other user of the system can access the System 100 via theUser Interface 200 through entry of a Uniform Resource Locator (URL)preferably via a suitable browser application 110, seen in FIGS. 2 and3, operating on a computer device. In response to entry of the URL, thebrowser application 110 directs the user to a survey landing page 212where the user is prompted for entry of their pre-assigned password.Alternatively, a dedicated data entry terminal may be used to access tothe System 100 via the User Interface 200 and enter the pre-assignedpassword. In response to entry of the pre-assigned password, the systempreferably enables the user to have access to an initial survey page,i.e., a “Welcome Page” 204 shown in the example in FIG. 2.

From the Welcome page 204 in the example in FIG. 2, the patient or otheruser of the system is asked at 206 to confirm that the patientdemographic data is correct. The process proceeds to an IntroductionPage 208 if the demographic data is confirmed; otherwise the processproceeds to a Contact Page (Exit) 209; and exits the process 210 torequest the user to enter the correct demographic information.

After the Introduction Page 208 is displayed to the user, at 212, theuser is asked if the user has a list of medications the patient takes,i.e., medications used by the patient. A message regarding theimportance of providing a medication list at 214 is displayed if theuser indicates he/she doesn't have the list, and the process 210 isexited. Alternatively, if the user indicates in response to the questionat 212, that the patient doesn't take medications, e.g., “I don't takemedications”, the process 210 proceeds to 226 in FIG. 2.

In response to the user indicating at 212 that they have a list of themedications taken, the system enables the patient to begin manual entryof name(s) of medication(s) at 216. The user is prompted to enter all orpart of the names of the medications used by the patient.

FIG. 1 illustrates an exemplary display 10 regarding a survey questionregarding medications according to an embodiment of the presentinvention. According to one aspect of certain embodiments of theinvention, a user enters the first few letters of the name of one of themedications used by the patient. The user is referred to hereinvariously as the “patient” or “user”, however, it should be appreciatedthat the user may be the patient, a healthcare provider, or anotherauthorized person using the system on behalf of the patient.

Preferably, a text box 13 is provided to display the letters typed bythe user for the medication name. If the letters entered by the user arenot recognized by the system as any known medication, the systempreferably asks the user to recheck the spelling on their pill bottle orprescription, and reenter letters in the name.

As shown in the example in FIG. 1, based on the letters entered by theuser for the medication, a drop down function appears with a muchabbreviated medication list. A two-tiered drop down list 18 in FIG. 1 isdisplayed in response to entry of a portion of the name, i.e., “asp”.Referring to FIGS. 1-3, this list 18 is generated by the survey enginein User Interface 200 by integrating information from the Expert System400 and the Medication Database 600. The order in which this list ispresented to the user is not strictly alphabetized, instead, the orderin the list is prioritized as described further below.

As shown at 218 in the exemplary embodiment in FIG. 2, the Expert System400 cross-references the Medication Database 600 and the Data WarehouseDatabase 800 for prioritizing the order in which the list of medicationsis presented to the user. According to certain embodiments, the ExpertSystem 400 provides the “first-tier” 14 of medications by generating its“best guess”, according to a machine learning algorithm, by comparingthe demographic data from the current user to historical data frommatched controls preferably stored in the Data Warehouse Database 800.The historical data is from other users of the method and for otherpatients, or from prior uses by the user or for the patient. Matchedcontrols refers to the historical data accumulated by the systemmatching the user in some way, including but not limited to, matchingbased on one or more of the age, gender, race, or other portion of thedemographic data. For example, as shown in FIG. 1, the user entered“asp” as one of the patient's medications. If 100 patients entered “asp”into the system and 99 of these patients said they take Aspirin and only1 said they take Aspartate, the system “learns” from this previous datain order to “know” that when a patient enters “Asp”, they likely takeAspirin, not Aspartate. Therefore, based on limited input from apatient, the system and method according to a preferred embodiment useshistorical data and the process of machine learning to formulate thedrop down list for the patient which prioritizes those medications inthe list which are most likely to be taken by a given patient. Theprioritized list is ordered from most likely to least likely, as itsfirst “best guess” of the likely medication to which the patient isreferring. Certain embodiments also include integrating data stored inthe repository from prior users, e.g., historical data on patient's,age, and gender, to further speciate the medication list. In addition,other patterns of matched controls, aside from age, gender, and race,may emerge in the historical data acquired using the system, that may beuseful in comparison and generation of the best guess.

A tier “two”, identified as 16 in FIG. 1, in the prioritized list 18contains other likely medications, other than the first tier best guessof the likely medication, that match the phrase typed in by the user inthe text box 13 and is provided from the Medication Database 600.

The user is preferably prompted to select the medication used by thepatient from the two-tiered list 18. At 220 in FIG. 2, in response tothe user selection, a prioritized list of potential indicationsassociated with use of the selected medication is displayed to thepatient, or other user, for selection, as explained in further detailbelow. Indications as used herein refer to disease states and/orsymptoms associated with a medication. The system and method accordingto embodiments of the present invention enables the patient to selecttheir specific medical conditions from this prioritized list; thusenabling the patients to easily reconcile their medications with theirassociated disease states and/or symptoms.

Since medications are used for specific indications, the system 100includes Medication associated with Condition Database 700 that linksall known medications to their respective indicated uses for all knownrelevant medical conditions and/or disease symptoms; thus all knownmedications are associated with known specific indications for which themedication may be used.

In response to the patient selecting their medication from the list ofmedications, at 220, the system presents the patient with a list ofplausible medical indications, ordered from most to least likely, as itsfirst “best guess” of the likely indications, e.g., conditions, diseaseand or symptom, for which the patient is using the medications. Theprioritized list of diseases and/or symptoms from the expert system ispreferably presented to the patient using lay person terminology.

For 220, the Expert System 400 preferably draws on the Survey Database500, the Medication/Condition Database 700, and the Data WarehouseDatabase 800 to formulate the list of potential indications for whichthe patient may use the selected medication. As shown at 222 in theexample in FIG. 2, the Expert System 400 prioritizes the display of thelist of indications, also referred to herein as “conditions”, presentedto the user. As shown at 222, the order in which this list ofindications is presented to the user is highly patient specific as it isbased, at least in part, on learning from prior users' interactions,according to a preferred embodiment. The order according to thepreferred embodiment is selected by Expert System 400 based ondemographic data from the current user in Survey Database 500,historical data from matched controls from Data Warehouse Database 800,and a comprehensive Medication/Condition database which has allmedications associated with their known indications.

Preferably, the Expert System 400 refines its “best guess” throughsequential questions to the patient until both the user and the systemare satisfied that current medications, as well as associated medicalconditions, have been correctly identified. According to an exemplaryembodiment, in response to a patient entering “Motrin” as one theirmedications, for example, the system and method automatically follows upwith the question, “Do you take Motrin for A) Fever B) Pain C) HeadachesD) Toothache or E) Arthritis?”. Depending on the patient's response,further follow-up questions may be presented to the user. For example,if a patient answers “B”, certain embodiments will follow up with aquestion asking the patient to specifically locate and describe theirpain. In this way, certain embodiments automatically prompt thepatient/user to reconcile their medications with their disease statesand/or symptoms and also provide a pathway for getting greaterspecificity about the answers to the questions.

Information associated with the refined “best guess” is stored withinthe Data Warehouse 800 as an incremental data point to help the system“learn” and improve its predictive power for each subsequent patientassessment, i.e., it uses a process known as “machine learning”.Additionally, each individual patient's results, i.e., survey, areaggregated with his/her demographic data in a standard format to createa complete medical history which can then be shared back with thepatient's clinical representative and used as input into the clinicaldecision making process for the patient's care.

According to another aspect of certain embodiments of the invention, thesystem integrates data stored in the repository from prior users toprioritize which disease states are most relevant for that particularpatient. For example, if the system knows the user who indicated takingMotrin is a 50 year old male scheduled for a knee replacement surgery,it has a knowledge base from inputs from other prior patients in orderto enable the system to suggest that this patient most likely takesMotrin for pain and arthritis. Thus, in response to this particularpatient entering “Motrin” as one of their medications, certainembodiments of the system automatically ask the user, “Do you takeMotrin to control the pain from arthritis?” as opposed to presenting thecomplete list of indications. In essence, the system utilizes whatappears to be reasoning capabilities to reach conclusions. In this case,the data available, i.e., 50 year old man scheduled for a kneereplacement, determines which inference rules will be used, i.e., it isa data driven system.

According to an aspect of preferred embodiments of the invention, thesequence of steps taken to formulate additional questions for anindividual user is dynamically synthesized with each new user. That is,the system preferably is not explicitly programmed when the system isbuilt, but rather formulates questions based on the current informationprovided about the specific patient, e.g., age, gender, chief complaint,etc., and historical data from matched controls.

According to an aspect of certain embodiments of the invention, thededucing of a patient's medical history is accomplished by an expertsystem by applying specific historical knowledge, rather than a specifictechnique. Thus, if the expert system does not produce the desiredresult, i.e., asks the patient if they take Motrin for the pain ofarthritis, but the patient really takes it for headaches, the expertsystem has the ability to expand its knowledge base. Thus, if the systemaccording to certain embodiments interviews 100 patients for kneereplacement surgery, for example, and 75 take Motrin for pain and 25take Motrin for headaches, it synthesizes this knowledge into itsdatabase; the more data the system accrues, the smarter and moreaccurate it becomes at deducing medical histories of future users.

From the ordered list of indications, the system enables the user toselect the indication for which the patient uses their medication. Thisallows the user to quickly and easily reconcile the patient'smedications with the patient's associated conditions. In response to thereconciliation, the system and method can move forward with theautomated creation of a medical history for the patient.

At 224 in FIG. 2, a summary is generated of all the patient'smedications associated with patient specific indication, i.e., diseaseand/or symptoms. Preferably, the summary is displayed to the user.

Since patients have medical conditions for which they may not take anymedications, e.g. heartburn, mitral valve prolapse, seasonal allergies,a General Questionnaire Database 900, illustrated schematically in FIG.3, contains additional questions to ensure the medical history recordedby System 100 is comprehensive. The user is preferably presented, at226, with a General Medical Questionnaire for capturing medicalconditions/symptoms for which patient uses no medications as well aspast surgical history.

In the example in FIG. 2, at 228, the user is presented with a finalsummary page which includes, in this example, patient demographics,medications associated with patient specific indications, and pastsurgical history. A summary of other information, preferably includingmedical conditions/symptoms for which patient uses no medications isalso included in the final summary page which is preferably stored inthe survey database 500.

All data from the survey completed by the user is preferably sent toProcessing Subsystem 300, illustrated in FIG. 3. The system ispreferably pre-programmed with all layperson's terms associated withwidely accepted medical terminology so that, in conjunction with thepatient completing the questionnaire, the system preferably generates amedical history using the widely accepted medical terminology. TheProcessing Subsystem 300 converts any remaining layperson terminologyback to the widely accepted medical terminology, if available, using theinformation pre-programmed within the Medication/Condition Database 700.Therefore, when Processing Subsystem 300 generates the medical historyfor an official medical record, the disease states preferably appearusing widely accepted medical terminology, not layperson terminology.For example, if the patient selects the layperson's term “Cold Sore”,the system preferably uses the term “Herpes Labialis” in generating themedical history.

The system and method preferably enables the medical history generatedby the expert system to be easily viewed on a network with passwordaccess or to be directly entered into an electronic medical record.

Having disclosed exemplary embodiments, modifications and variations maybe made to the disclosed embodiments while remaining within the scope ofthe invention as described by the following claims.

1. A method for generating a medical history for a patient, comprising:obtaining from a user an identification of each of the medications thepatient is taking; obtaining demographic data for the patient; creatinga list of probable additional medications using a computer processor,including determining which known medications are the probablemedications that are more likely taken by the patient based on themedication identifications received from the user, a first knowledgebase of medications, and based on the patient's demographic data;displaying the list of probable medications to the user; and receiving aselection from the user of one of the probable medications on the listof probable medications; for each one of the selected probablemedications: (i) creating a list of probable medical indicationsassociated with the respective medication, wherein the probable medicalindications are diseases or symptoms, including determining which knownmedical indications are probable medical indications for which thepatient most likely takes the identified medication based on a secondknowledge base of known medical indications for the respectivemedication; (ii) displaying the list of medical indications to the user;and (iii) receiving a selection from the user of one or more of theprobable medical indications on the list; and generating a medicalhistory for the patient based on the user selected probable medicalindications and respective medications.
 2. The method of claim 1,further comprising obtaining historical data for other users of themethod; and wherein the determining of both the probable medications andthe probable medical indications are further based on the patient'sdemographic data and the historical data.
 3. The method of claim 2,wherein the historical data from other users of the method comprisesdata for other patients who match at least a portion of the demographicdata of the patient.
 4. The method of claim 1, further comprisingordering the list of probable medications starting with the knownmedications most likely taken by the patient.
 5. The method of claim 1,wherein the list of probable medical indications is ordered from themost likely probable medical indications sequentially followed by lesslikely probable medical indications, with the most likely probablemedical indications displayed at the top of the list.
 6. The method ofclaim 1, wherein the determining of both the probable medications andthe probable medical indications are further based on the patient'sdemographic data.
 7. The method of claim 1, further comprising obtaininghistorical data for other patients who have used the method; and whereinthe determining of both the probable medications and the probablemedical indications are further based on the historical data.
 8. Themethod of claim 7, wherein the historical data comprises historical datafor other patients who match at least a portion of the demographic dataof the patient.
 9. The method of claim 1, further comprising:selectively for each one of the selected probable medications,displaying a question to the user, wherein the question is based atleast on the selected probable medication, demographic data for thepatient, and historical data for other patients from other users of themethod.
 10. The method of claim 9, wherein the displaying of the list ofprobable medical indications to the user includes ordering of theprobable medical indications on the list based on a response receivedfrom the user to the question.
 11. The method of claim 1, furthercomprising dynamically generating questions in response to previousresponses received from the user, to generate additional information forinclusion in the patient's medical history.
 12. The method of claim 2,wherein the determining is further based on historical data for thepatient.
 13. The method of claim 1, wherein the user selected probablemedical indications and respective medications are provided in themedical history using widely accepted medical terminology.
 14. Themethod of claim 2, wherein the historical data from other users of themethod includes inputs provided using the method.
 15. The method ofclaim 2, wherein the demographic data includes at least one of thepatient's age, gender, diseases, and symptoms.
 16. The method of claim1, wherein the list of medical indications is presented to the userusing lay person terminology.
 17. The method of claim 1, wherein the atleast a portion of the name of the medication used by the patientcomprises at least the first two letters of the name.
 18. The method ofclaim 1, further comprising enabling secure viewing of the generatedmedical history via a network using password access.
 19. The method ofclaim 1, further comprising entering the generated medical history intoan electronic medical record.
 20. The method of claim 1, wherein themedical history is generated via an expert system and machine learning.21. The method of claim 1, further comprising presenting one or morequestions to the user regarding medical conditions, symptoms, and pastsurgical history for the patient for which the patient uses nomedications; and wherein the medical history includes information basedon user responses to the one or more questions.
 22. The method of claim1, wherein the step of obtaining from a user an identification of eachof the medications the patient is taking comprises receiving input fromthe user of at least a portion of the name of each of the medicationsthe patient is taking, and wherein the step of creating a list ofprobable medications further includes determining which knownmedications are the probable medications that are more likely taken bythe patient based on the at least a portion of the medication namereceived from the user.
 23. A system for generating an automated medicalhistory of a patient, comprising: a first database comprisingdemographic data for the patient; a user interface for receiving fromthe user at least a portion of the names of each of the medications; asecond database for storing a library of known medications; a thirddatabase for storing a library of the known medications and theirrespective indications; an expert system for creating a list of probablemedications based on a determination of which known medications areprobable medications based on the at least a portion of the medicationname received from the user, the known medications in the seconddatabase, and the patient's demographic data in the first database;wherein the user interface is further for displaying the list ofprobable medications to the user, and for receiving selection from theuser of one of the probable medications from the list of probablemedications; the expert system is further for creating a list ofprobable medical indications associated with the selected probablemedication based on a determination of which known medical indicationsare probable medical indications for which the patient most likely takesthe selected medication based on the patient's demographic data storedin the first database and the known medications and their respectivemedical indications stored in the third database; the user interface isfurther for displaying the list of probable medical indications to theuser and for receiving selection from the user one or more of theprobable medical indications on the list of probable medicalindications; and using the expert system, generating a medical historyfor the patient that includes at least the selected probable medicationand the selected one or more probable medical indications.
 24. Thesystem of claim 23, further comprising a fourth database for storingquestions for capturing medical conditions, symptoms, and past surgicalhistory for the patient for which the patient uses no medications. 25.The system of claim 24, wherein the expert system is further forfacilitating the input of information via the user interface bydynamically generating additional questions in response to previousresponses provided by the user.
 26. The system of claim 23, wherein theexpert system includes machine learning capabilities.